(updated for server version 5.24 or later)
The MOMI subsystem on the NonStop system is initially launched via a TACL obey file which starts the initial and main process named by default $MOMI. The initial process starts other processes that collectively support the MOMI environment.
When a user 'logs on' to a MOMI PC Client, a logon server process is launched that assumes given User ID. When a sensitive command is issued at the client, such as viewing the content of a Spooler Job, a process is launched from the logon server to perform the sensitive commands under the users authority and not under the authority of the main $MOMI process.
MOMI does NOT contain privileged code and should NOT be licensed via FUP. However, execution of certain operations, such as the generation of an ICMP PING message, requires a Super.Group level of authority to open a raw socket. If MOMI is started under the Super.Super (255,255) or a Super.Group (255,*) user the necessary level of authority is available. In the case where the administrator of MOMI does not desire to operate the majority of MOMI under a Super.* user, the needed "Super Group" level of authority can be obtained as needed via a separate object file named BWSSG (this object is discussed below). BWSSG is manually created during installation.
The simplest configuration for MOMI is to start it under Super.Super, followed by Super.Group and lastly under a "normal" User ID, perhaps one specifically created for MOMI, and then also creating BWSSG.
Below are the security guidelines for various files / subvolume:
The MOMI executable.
Must be secured to allow Execute for all users. For example, a Guardian security string of "UUNU". Additionally, in order to allow the creation of SAVEABEND files (used in troubleshooting), READ access should also be considered for a resulting security string of "NUNU".
If $MOMI is started under Super.Super or the Super.Group, this file is not needed.
BWSSG is created by the user and is a copy (i.e. FUP DUP) of BWMOMI (or BWMOMIi, BWMOMIx) and functions as a helper program to perform operations such as TCP/IP PING (the ICMP Echo command) and adjustment (if enabled) of the System time .
File security must allow Execute for all users (i.e. "UUNU"). To allow the creation of SAVEABEND files (used in troubleshooting), READ access should also be considered for a resulting security string of "NUNU".
Subvolume of BWMOMI
MOMI creates configuration, log and work files in the subvolume where the object resides. Additionally, other files distributed with the executable may be accessed. The User ID MOMI runs under must have read / write / execute / purge / create access to this subvolume. Consider not using SAFEGUARD for this subvolume.
The files created by default in this location can be relocated with the following CONFMOMI keywords:
To relocate existing files - stop MOMI, manually move the file(s), add the keyword(s) to CONFMOMI, and then restart MOMI.
Subvolume of MOMI history files (CONFMOMI keyword HSTnnDB)
MOMI must be given read / write / create / purge access to the subvolume(s) specified for these files.
MEASURE support files (such as MEASFH).
MOMI makes extensive use of MEASURE. These files must allow read / execute access.
EMS distributor program (used to read EMS log files).
The file must allow execute access.
ProcessH support file.
MOMI uses this file in ProcessH "System" code report on Integrity and later systems. The file must allow read access.
ProcessH support file.
MOMI uses this file in ProcessH "System" code report on Integrity and later systems. The file must allow read access.
Tape programmatic server.
MOMI uses this to report on tape status. The file must allow execute access.
Virtual memory access utility.
MOMI uses this to report on virtual memory usage. The file must allow execute access.
O/S release information (i.e. G06.29.02).
The file must allow read access.
TMF programmatic server.
MOMI uses this to report on TMF status. The file must allow execute access.
ProcessH support file - 16-bit code.
MOMI uses this file in ProcessH "System" code report on S-Series systems. The file must allow read access.
ProcessH support file.
MOMI uses this file in ProcessH "System" code report. The file must allow read access.
ProcessH support file.
MOMI uses this file in ProcessH "System" code report on S-Series systems. The file must allow read access.
SQL/MP compilation utility.
The display of SQL/MP information is the result of dynamic SQL statements. This file must allow read / execute access.
MOMI provides SQL/MP information by reading this subsystem's catalogs. MOMI needs read access to the Catalog of the System to provide information on the SQL/MP screens. Optionally, but recommended, MOMI should be granted read access to all other SQL/MP catalogs on the system. Where access is not granted, a security error is displayed.
$SYSTEM.SYSTEM.EVENTCX (this file is optional)
EMS user defined cause / effect / recovery information.
MOMI makes use of this file to display EMS user defined cause / effect / recovery information. MOMI needs read / write access to this file. MOMI Client access controls the ability to display / alter information. The location of this file may be overridden with the CONFMOMI keyword EVENTCX.
EMS HTML cause / effect / recovery information.
MOMI makes use of this file to display EMS cause / effect / recovery information. MOMI needs read access to this file.
EMS log file subvolume.
In order to display EMS messages from $0, the log files must allow read access. Use EMSCINFO $0 to display the current log file settings and EMSCCTRL $0,<command> to alter the settings. Existing files will need to have their file security manually altered via FUP.
EMS log file subvolume for hardware events.
In order to display EMS messages from $ZLOG, the log files must allow read access. Use EMSCINFO $ZLOG to display the current log file settings and EMSCCTRL $ZLOG,<command> to alter the settings. Existing files will need to have their file security manually altered via FUP.